-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add backticks to the gramar #20
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just the one comment
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one comment for the test, otherwise LGTM
parse_to("`foo.bar.baz`", ["foo.bar.baz"]) | ||
parse_to("`foo`.`bar-baz`", ["foo", "bar-baz"]) | ||
parse_to("`foo`.`bar-baz`", ["foo", "bar-baz"]) | ||
parse_to("`💩`", ["💩"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💩
tests/test_parser.py
Outdated
parse_to("`foo bar baz`", ["foo bar baz"]) | ||
parse_to("`foo.bar.baz`", ["foo.bar.baz"]) | ||
parse_to("`foo`.`bar-baz`", ["foo", "bar-baz"]) | ||
parse_to("`foo`.`bar-baz`", ["foo", "bar-baz"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two lines above are the same. did you mean something else for the second one?
* Add backtick support and tests * Add engine tests for backtick * Add note to changelog * Add additional backtick test * Unduplicate backtick test
Issues
Relates to #15
Closes #19
Details
Fairly straightforward. Added `backtick` support to the grammar and parser.
Validated that the engine is still working as expected.